Sourced from naja's releases.

3.3.0

New features

• ✨ You can now unambiguously distinguish the initial history state update via the isInitial property of the buildState event. (#418, #420)

Minor changes and bugfixes

• 🐞 Naja's history integration is now properly re-initialized after full page reloads. (#418, #420)
• 🐞 Snippet updates are now handled synchronously whenever possible, making for a more predictable order of dispatched afterUpdate event. (#416, #417)

3.2.1

Minor changes and bugfixes

• 🐞 Naja now does a better job at instructing browsers to use the correct title in the history entry. (#406, #407)
• 🔧 The naja package now exports all event types and some other auxiliary types so that you can unleash full strictness onto your TypeScript codebase. (#408)

3.2.0

New features

• ✨ UIHandler.submitForm() helper method now accepts a submitter element as its first parameter, in addition to a form. However, the native form.requestSubmit() method is the recommended way to manually dispatch form submissions to Naja in modern browsers.

Minor changes and bugfixes

• 🔧 UI binding to forms has been simplified (#401, #402, thanks @​filiphlm). Naja now does not bind itself onto submitter elements, instead it listens only on submit events of forms. The interaction event's element property continues to refer to the submitter element when available.
• 🔧 Naja switched to the exports field in package.json

Compatibility considerations

Naja continues to hold its compatibility promise of working correctly "in the latest versions of Chromium (Chrome and Edge), Firefox, and WebKit (Safari)."

With this release, Naja newly relies on APIs that might not be available in some older versions of these browsers. If you still need to support these, please check the compatibility and available polyfills for the SubmitEvent.submitter property, and the submitter parameter in FormData() constructor.

3.1.0

New features

• ✨ UIHandler provides a helper called processInteraction() that allows developers to process any custom interactions through Naja, including dispatching the interaction event. (#388)

Minor changes and bugfixes

• 🐞 UIHandler binds onto form buttons without explicit type="submit". (#397)

3.0.0

Naja 3.0 is an evolutionary release and should not come with any breaking changes for the majority of users. The breaking changes are mostly expected to affect advanced users, and developers who build custom extensions on top of Naja.

That said, there have been some changes in the inner workings of the snippet cache that may alter the behaviour, so it is strongly recommended that you properly test your application against the 3.x release.

New features

• ✨ SnippetHandler supports asynchronous snippet update operations, such as using View Transitions API. (#383) You can now wrap snippet updates in transitions, and rely on Naja dispatching the afterUpdate event only after the update has been completed.

... (truncated)

• aa9fa65 chore: fix publish pipeline
• e4bbe5d Release 3.3.0
• 4798f76 chore: update dependencies
• 94b5d8c HistoryHandler: call replaceInitialState in popstate when popping to a Naja-p...
• 6c22d1f HistoryHandler: distinguish initial replaceState call via an explicit boolean...
• 91ee116 SnippetHandler: prefer to process snippet update synchronously if possible (#...
• a719482 chore: remove gpg signing from production build
• 1c0d108 chore: migrate to npm trusted publishing
• f8753e9 chore: update dependencies
• f9009d7 docs: replace bundlephobia badge with bundlejs
• Additional commits viewable in compare view

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for naja since your current version.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)